Finally coming back to this ... and found the issue :-)

DBGWebPage *NewPage = new DBGWebPage(webGUI);

The new Page was not a child of the correct object.
I checked pointers as suggested.
The connect of the JS bridge showed no issues.
However, the first call from JS (signal javaScriptWindowObjectCleared() calling my populateJavaScriptWindowObject())
crashed on

QWebFrame * webGUIframe = qobject_cast<QWebFrame *>(sender()); QWebView * webGUI = (QWebView*)(webGUIframe->parent())->parent();

obviously because it was pointing to 'nothing' instead of a QWebView.
Thank you guys for all the hints.

Thanks a lot !! :D @Wieland

Hi,

QtWebKit for Android and iOS ? Highly unlikely, since both platform forbids the use of non-native web views and there was no ports.

Taking a quick look at the QtWebView module, there's a QtWebEngine backed WebView when that module is available. So currently you should be able to use that module on all the platforms you are interested in provided that you use a compiler that is supported by QtWebEngine. Note that the compiler constraint doesn't come from Qt but from the Chromium project.

@0hno Cool. Thanks for sharing.